home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980424-19980901
/
000125_news@newsmaster….columbia.edu _Mon May 25 09:39:39 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
6KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id JAA16536
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 25 May 1998 09:39:38 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id JAA16216
for kermit.misc@watsun; Mon, 25 May 1998 09:39:37 -0400 (EDT)
Path: news.columbia.edu!newsfeed.nyu.edu!feeder.qis.net!news-peer.gip.net!news-penn.gip.net!news.gsl.net!gip.net!news.belnet.be!news.rediris.es!newsfeed.mad.ibernet.es!news.mad.ibernet.es!not-for-mail
From: clizzard@sunnydesert.com (Diego Berge)
Newsgroups: comp.protocols.kermit.misc,comp.sys.hp48
Subject: Re: Kermit on the HP48 (Was: One-Way Transfer)
Date: 23 May 1998 10:39:44 GMT
Organization: Telefonica Transmision de Datos
Lines: 24
Message-ID: <6k691g$bn3$2@talia.mad.ibernet.es>
References: <35646665.EBB3868B@theriver.com> <wkvhqye9g4.fsf@jhuapl.edu> <6k42pd$a3m$1@apakabar.cc.columbia.edu> <wk67iy1b8j.fsf@jhuapl.edu> <6k4ef6$g6p$1@apakabar.cc.columbia.edu> <wk4syi58y0.fsf@jhuapl.edu>
NNTP-Posting-Host: ppp41.198.redestb.es
Mime-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
X-Newsreader: WinVN 0.99.9 (Released Version) (16bit)
Xref: news.columbia.edu comp.protocols.kermit.misc:8786 comp.sys.hp48:81422
Hi,
PFJI
In article <wk4syi58y0.fsf@jhuapl.edu>, collibf1@jhuapl.edu says...
>
>> set carrier-watch off ; (Does the HP-48 assert DCD? If so, use ON.)
The 48 doesn't detect DCD.
>
>It has no hardware flow control, if that's what you mean.
>
>> set flow none ; (or Xon/Xoff)
>
>Should be none.
It does have. You can activate Xon/Xoff flow control by editing IOPAR
manually { x x 1 1 x } to activate xon/xoff both in transmit and receive. Read
the manual, it's in there.
Regards,
Diego Berge.
From news@newsmaster.cc.columbia.edu Mon May 25 12:07:19 1998
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id MAA05698
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 25 May 1998 12:07:19 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id MAA24216
for kermit.misc@watsun; Mon, 25 May 1998 12:07:19 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc,comp.sys.hp48
Subject: Re: Kermit on the HP48 (Was: One-Way Transfer)
Date: 25 May 1998 16:07:18 GMT
Organization: Columbia University
Lines: 54
Message-ID: <6kc4vm$ssl$1@apakabar.cc.columbia.edu>
References: <35646665.EBB3868B@theriver.com> <wk67iy1b8j.fsf@jhuapl.edu> <6k4ef6$g6p$1@apakabar.cc.columbia.edu> <wk4syi58y0.fsf@jhuapl.edu>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:8787 comp.sys.hp48:81425
In article <wk4syi58y0.fsf@jhuapl.edu>,
Skip Collins <collibf1@jhuapl.edu> wrote:
: fdc@watsun.cc.columbia.edu (Frank da Cruz) writes:
: > Most Kermit programs prefix all control characters by default when sending
: > a file. Kermit 95 is the exception, since most Windows 95 users demand
: > "high performance". Kermit 95's default is to unprefix a fairly safe
: > subset of control characters.
:
: If I had to bet on what trips up most K95-HP48 connections I would wager it
: is control-char unprefixing. I will try it with mskermit when I get a
: chance. What command should I issue to mimic the K95 default?
:
Something like this:
SET CONTROL UNPREFIX ALL
SET CONTROL PREFIX 0 1 13 17 19 129 141 145 147
: > : I think the physical link is transparent to control characters. But
: > : perhaps the hp48 kermit software assumes prefixing.
: >
: > The cardinal rule of any communications protocol is "be conservative in
: > what you send, be liberal in what you receive". The HP48 has it backwards.
: > There is no prohibition in the protocol definition against sending bare
: > control characters,
:
: This seems to contradict "Kermit: A File Transfer Protocol", 1987 ed.,
: which states on page 248, under the heading Encoding Summary: "Prefix
: encoding for control characters is mandatory."
:
No good deed goes unpunished. The conservative original design of the
protocol (to protect users from nontransparent connections) resulted in
so much heckling from the ZMODEM contingent that we now allow the user to
specify a list of control characters that may be unprefixed. This is,
strictly speaking, in violation of the protocol definition, and as such
it is not (and, as explained previously, can not be) negotiated at the
protocol level.
Nevertheless, the sample code that accompanies the protocol definition
(op.cit., p.231) allows for bare control characters to be received.
: As long as you are cataloguing peculiarities, the HP48 sends packet
: sequence numbers that are larger than 63. One can compensate by doing
: mod63 before verifying. Is this right?
:
No. Packets numbers should be 0-63, period. The packet length field is
one byte long, and contains a printable character. Even if the receiver
chopped off the high bits from an incoming packet number, this would work
only up to packet 95, since the packet after that would be out of sequence.
Thus if it's true that HP does not wrap packet sequence numbers from 63 to
0, then it would appear that it could never, under any circumstances, send
files or objects that do not fit into 64 or 96 packets, depending on how
the Kermit receiver is coded.
- Frank